Skip to content

Add 10 new SEO blogs#2996

Open
adityaoberai wants to merge 12 commits into
mainfrom
aditya/add-new-seo-blogs
Open

Add 10 new SEO blogs#2996
adityaoberai wants to merge 12 commits into
mainfrom
aditya/add-new-seo-blogs

Conversation

@adityaoberai
Copy link
Copy Markdown
Contributor

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

@appwrite
Copy link
Copy Markdown

appwrite Bot commented May 12, 2026

Appwrite Website

Project ID: 69d7efb00023389e8d27

Sites (1)
Site Status Logs Preview QR
 website
69d7f2670014e24571ca
Failed Failed View Logs Preview URL QR Code

Website (appwrite/website)

Project ID: 684969cb000a2f6c0a02

Sites (1)
Site Status Logs Preview QR
 website
68496a17000f03d62013
Queued Queued View Logs Preview URL QR Code


Tip

Appwrite has crossed the 50K GitHub stars milestone with hundreds of active contributors

@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps Bot commented May 12, 2026

Greptile Summary

This PR adds 10 new SEO-targeted blog posts covering various aspects of vibe coding, including startup ideas, agency workflows, backend/frontend comparisons, security mistakes, and deployment guides. All posts are authored by aditya-oberai with staggered publish dates from May 11–16, 2026, and matched cover images.

  • All 10 posts carry unlisted: true (discussed in the previous review thread) and share a consistent structure with frontmatter FAQs and internal cross-links pointing to existing posts in the repo.
  • Cross-references to /blog/post/backend-checklist-vibe-coded-apps, /blog/post/comparing-vibe-coding-tools, and /blog/post/vibe-coding-security-best-practices are all valid — those posts exist in the repository.
  • One minor grammar error was found in best-frontend-frameworks-for-vibe-coding: "one of the strongest default" should be "defaults".

Confidence Score: 5/5

This PR adds only new blog content (markdoc files and cover images) with no changes to application logic, routing infrastructure, or build configuration.

All changes are additive content files. Internal cross-links resolve to existing posts. No logic, configuration, or schema is modified. The single grammar nit found has no functional impact.

No files require special attention.

Important Files Changed

Filename Overview
src/routes/blog/post/25-startup-ideas-you-can-build-with-vibe-coding/+page.markdoc New blog post listing 25 startup ideas for vibe coding; well-structured with correct Teams link at /docs/products/auth/teams; marked unlisted: true (flagged in previous thread)
src/routes/blog/post/agencies-vibe-coding-client-projects/+page.markdoc New blog post on agency vibe coding workflows; internal links all valid; marked unlisted: true
src/routes/blog/post/best-backend-for-vibe-coding-apps/+page.markdoc New backend comparison post; paragraph duplication flagged in previous thread; unlisted: true
src/routes/blog/post/best-frontend-frameworks-for-vibe-coding/+page.markdoc New framework comparison post; minor grammar issue ("strongest default" should be "defaults") at line 40; unlisted: true
src/routes/blog/post/can-vibe-coding-replace-junior-developers/+page.markdoc New post on vibe coding and junior developer roles; clean cross-references; unlisted: true
src/routes/blog/post/deploy-vibe-coding-projects-to-production/+page.markdoc New step-by-step deployment guide; Teams link now correctly points to /docs/products/auth/teams; unlisted: true
src/routes/blog/post/hidden-costs-of-vibe-coding-platforms/+page.markdoc New post on hidden vibe coding costs; all cross-referenced posts exist in the repo; unlisted: true
src/routes/blog/post/how-vibe-coding-is-changing-software-development/+page.markdoc New overview post on vibe coding's impact; unlisted: true
src/routes/blog/post/vibe-coding-security-mistakes/+page.markdoc New security-focused post covering 16 mistakes; compliance link on line 118 goes to https://cloud.appwrite.io rather than a dedicated compliance page; unlisted: true
src/routes/blog/post/vibe-coding-vs-traditional-development/+page.markdoc New comparison post; date: 2026-05-16 is a future date consistent with the staggered publishing schedule; unlisted: true

Reviews (6): Last reviewed commit: "update dates" | Re-trigger Greptile

Comment thread src/routes/blog/post/deploy-vibe-coding-projects-to-production/+page.markdoc Outdated
Comment thread src/routes/blog/post/best-backend-for-vibe-coding-apps/+page.markdoc Outdated
answer: "Anything with a clear user, a narrow scope, and a small set of backend primitives: auth, a few tables, file uploads, a payment hook, maybe a scheduled function. Vibe coding tools like Cursor, Claude Code, Windsurf, Lovable, and Bolt are excellent at scaffolding apps in this shape. The ideas in this post all fit that profile."
- question: "Do I need to know how to code to build these?"
answer: "It helps. Tools like Lovable and Bolt let non-developers ship a working version, but every idea here will hit a wall the first time a user reports a real bug. Knowing enough to read a diff, understand permissions, and check that secrets are not in the client bundle is the difference between a demo and a startup."
- question: "What backend should I use for these ideas?"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 All 10 posts are marked unlisted: true

The PR title describes these as "SEO blogs", but unlisted: true prevents them from appearing in the blog listing and from being crawled and indexed. This pattern appears on all 10 new posts. If public visibility is intended at merge time, this flag should be removed or set to false across all 10 posts. If this is a staged rollout reviewed before going live, no action is needed here — but it is worth confirming the flag will be cleared before the SEO value is expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants